Wireless link management techniques for wireless charging systems

ABSTRACT

Wireless link management techniques for wireless charging systems are described. According to some such techniques, a power receiving unit (PRU) may be configured to observe a rectifier voltage while operating in a charge complete connected (CCC) mode according to which it possesses a wireless connection with a power transmitting unit (PTU) operating in a power save state. In various embodiments, the PRU may be configured to observe the rectifier voltage in an attempt to detect power beacons generated by the PTU. In some embodiments, the PRU may be configured to maintain the wireless connection if it detects power beacons, and to terminate the wireless connection if it does not detect any beacons. Other embodiments are described and claimed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, claims the benefit of andpriority to previously filed U.S. patent application Ser. No.15/199,811, filed Jun. 30, 2016, entitled “WIRELESS LINK MANAGEMENTTECHNIQUES FOR WIRELESS CHARGING SYSTEMS”, which claims the benefit ofand priority to previously filed U.S. Provisional Patent ApplicationSer. No. 62/292,035 filed Feb. 5, 2016, entitled “WIRELESS LINKMANAGEMENT TECHNIQUES FOR WIRELESS CHARGING SYSTEMS”, which are herebyincorporated by reference in their entireties.

This application relates to International Patent Application entitled“WIRELESS LINK MANAGEMENT TECHNIQUES FOR WIRELESS CHARGING SYSTEMS,”International Application Serial Number PCT/US17/16738, filed Feb. 6,2017. The contents of the aforementioned application are incorporatedherein by reference.

TECHNICAL FIELD

Embodiments described herein generally relate to wireless power transfersystems.

BACKGROUND

In a wireless power transfer system, a power transmitting unit (PTU) maybe capable of wirelessly transferring power to compatible devices thatare located within a transfer field of that PTU. In order to effectpower transfer, the PTU may apply current to a resonator coil, which maytransfer power to one or more power receiving units (PRUs) via resonantinductive coupling with resonator coils of those PRUs.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a first operating environment.

FIG. 2 illustrates an embodiment of a second operating environment.

FIG. 3 illustrates an embodiment of a third operating environment.

FIG. 4 illustrates an embodiment of a fourth operating environment.

FIG. 5 illustrates an embodiment of a first logic flow.

FIG. 6 illustrates an embodiment of a second logic flow.

FIG. 7 illustrates an embodiment of a storage medium.

FIG. 8 illustrates an embodiment of a device.

FIG. 9 illustrates an embodiment of a wireless network.

DETAILED DESCRIPTION

Various embodiments may be generally directed to wireless linkmanagement techniques for wireless charging systems. According to somesuch techniques, a power receiving unit (PRU) may be configured toobserve a rectifier voltage while operating in a charge completeconnected (CCC) mode according to which it possesses a wirelessconnection with a power transmitting unit (PTU) operating in a powersave state. In various embodiments, the PRU may be configured to observethe rectifier voltage in an attempt to detect power beacons generated bythe PTU. In some embodiments, the PRU may be configured to maintain thewireless connection if it detects power beacons, and to terminate thewireless connection if it does not detect any beacons. Other embodimentsare described and claimed.

Various embodiments may comprise one or more elements. An element maycomprise any structure arranged to perform certain operations. Eachelement may be implemented as hardware, software, or any combinationthereof, as desired for a given set of design parameters or performanceconstraints. Although an embodiment may be described with a limitednumber of elements in a certain topology by way of example, theembodiment may include more or less elements in alternate topologies asdesired for a given implementation. It is worthy to note that anyreference to “one embodiment” or “an embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment is included in at least one embodiment. The appearances ofthe phrases “in one embodiment,” “in some embodiments,” and “in variousembodiments” in various places in the specification are not necessarilyall referring to the same embodiment.

Embodiments herein are generally directed to wireless power transfersystems. Various embodiments may involve wireless power transfersperformed according to one or more wireless power transfer standards.Wireless power transfer technologies and/or standards that may be usedin some embodiments may include, for example, Rezence standardspromulgated by the Alliance for Wireless Power, Qi standards promulgatedby the Wireless Power Consortium, and the Power 2.0 standard promulgatedby the Power Matters Alliance. Additional examples of wireless powertransfer technologies and/or standards that may be used in someembodiments may include technologies and/or standards that may bepromulgated by the organization formed by the 2015 merger of theAlliance for Wireless Power and the Power Matters Alliance. Theembodiments are not limited to these examples.

Various embodiments may involve wireless communications performedaccording to one or more wireless communications standards. For example,some embodiments may involve wireless communications in Bluetooth LowEnergy (also known as Bluetooth Smart) wireless networks according toBluetooth Core Specification 4.2, released December 2014, and/or anypredecessors, progeny, and/or variants thereof. Additional examples ofwireless communications technologies and/or standards that may be usedin various embodiments may include—without limitation—IEEE wirelesscommunication standards such as the IEEE 802.11, IEEE 802.11a, IEEE802.11b, IEEE 802.11g, IEEE 802.11n, IEEE 802.11u, IEEE 802.11ac, IEEE802.11 ad, IEEE 802.11af, and/or IEEE 802.11ah standards,High-Efficiency Wi-Fi standards developed by the IEEE 802.11 HighEfficiency WLAN (HEW) Study Group, Wi-Fi Alliance (WFA) wirelesscommunication standards such as Wi-Fi, Wi-Fi Direct, Wi-Fi DirectServices, Wireless Gigabit (“WiGig”), WiGig Display Extension (WDE),WiGig Bus Extension (WBE), WiGig Serial Extension (WSE) standards and/orstandards developed by the WFA Neighbor Awareness Networking (NAN) TaskGroup. Some embodiments may involve wireless communications performedaccording to one or more next-generation 60 GHz (“NG60”) wireless localarea network (WLAN) communications standards and/or one or moremillimeter-wave (mmWave) wireless communication standards.

Various embodiments may involve wireless communications performedaccording to one or more broadband wireless communications standards.For example, some embodiments may involve wireless communicationsperformed according to one or more 3rd Generation Partnership Project(3GPP), 3GPP Long Term Evolution (LTE), and/or 3GPP LTE-Advanced (LTE-A)technologies and/or standards, including their predecessors, revisions,progeny, and/or variants. Additional examples of broadband wirelesscommunication technologies/standards that may be utilized in variousembodiments may include—without limitation—Global System for MobileCommunications (GSM)/Enhanced Data Rates for GSM Evolution (EDGE),Universal Mobile Telecommunications System (UMTS)/High Speed PacketAccess (HSPA), and/or GSM with General Packet Radio Service (GPRS)system (GSM/GPRS), IEEE 802.16 wireless broadband standards such as IEEE802.16m and/or IEEE 802.16p, International Mobile TelecommunicationsAdvanced (IMT-ADV), Worldwide Interoperability for Microwave Access(WiMAX) and/or WiMAX II, Code Division Multiple Access (CDMA) 2000(e.g., CDMA2000 1×RTT, CDMA2000 EV-DO, CDMA EV-DV, and so forth), HighPerformance Radio Metropolitan Area Network (HIPERMAN), WirelessBroadband (WiBro), High Speed Downlink Packet Access (HSDPA), High SpeedOrthogonal Frequency-Division Multiplexing (OFDM) Packet Access (HSOPA),High-Speed Uplink Packet Access (HSUPA) technologies and/or standards,including their predecessors, revisions, progeny, and/or variants.Further examples of wireless communications technologies and/orstandards that may be used in some embodiments may include—withoutlimitation—machine-type communications (MTC) standards such as thoseembodied in 3GPP Technical Report (TR) 23.887, 3GPP TechnicalSpecification (TS) 22.368, and/or 3GPP TS 23.682, and/or near-fieldcommunication (NFC) standards such as standards developed by the NFCForum, including any predecessors, revisions, progeny, and/or variantsof any of the above.

FIG. 1 illustrates an example of an operating environment 100 that maybe representative of various embodiments. In operating environment 100,a wireless charging station 101 comprises a power transmitting unit(PTU) 102, which may be operable to wirelessly transfer power to capabledevices within a transfer region 104. In some embodiments, PTU 102 maybe operable to wirelessly transfer power to capable devices withintransfer region 104 via resonant inductive coupling, using a transmitresonator. It is worthy of note that the size and shape of transferregion 104—as well as its position and orientation relative to wirelesscharging station 101 and PTU 102—may vary from embodiment to embodiment,and are not limited to the example depicted in FIG. 1.

In various embodiments, PTU 102 may be configured to operate in a powersave state when there are no devices requiring wireless charging withintransfer region 104. In some embodiments, while operating in the powersave state, PTU 102 may periodically generate short beacons 106 in orderto detect the presence of wirelessly-chargeable devices within transferregion 104. In various embodiments, PTU 102 may detect the presence of anew device based on a change in the impedance upon the transmitresonator. In some embodiments, while operating in the power save state,PTU 102 may periodically generate long beacons 108 in order to enabledevices that may be present within transfer region 104 to identifythemselves to PTU 102. In various embodiments, any given long beacon 108may enable such a device to power on for a period of time long enough totransmit an advertisement to PTU 102. The embodiments are not limited inthis context.

FIG. 2 illustrates an example of an operating environment 200 that maybe representative of some embodiments. In operating environment 200, awirelessly-chargeable device (WCD) 210 is present within transfer region104, and comprises a power receiving unit (PRU) 212. In this example,WCD 210 is the only wirelessly-chargeable device present within transferregion 104. In various embodiments, a long beacon 108 generated by PTU102 may provide PRU 212 with enough power to enable PRU 212 to transmitan advertisement 214 to PTU 102. In some embodiments, in response toadvertisement 214, PTU 102 may transmit a connection request message toPRU 212, and a wireless communication connection 216 may be establishedbetween PTU 102 and PRU 212. In various embodiments, wirelesscommunication connection 216 may comprise a Bluetooth Low Energy (BLE)connection. The embodiments are not limited in this context.

In some embodiments, if a battery of WCD 210 needs to be charged, PRU212 may communicate with PTU 102 via wireless communication connection216 in order to request wireless power transfer. In various embodiments,in order to wirelessly transfer power to PRU 212, PTU 102 may operate ina power transfer state. In some embodiments, PRU 212 may wirelesslyreceive power from PTU 102 via resonant inductive coupling, using areceive resonator. In various embodiments, once the battery is fullycharged, PRU 212 may transmit a charge completion notification 218 toPTU 102 via wireless communication connection 216 in order to notify PTU102 that wireless power transfer is no longer required. In someembodiments, PRU 212 may send charge completion notification 218 to PTU102 by setting a Charge Complete bit in a PRU Dynamic ParameterCharacteristic or PRU Alert to a value of 1. In various embodiments, inresponse to receipt of charge completion notification 218—and in view ofthe fact that WCD 210 is the only wirelessly-chargeable device locatedwithin transfer region 104—PTU 102 may determine that there are nolonger any devices requiring wireless charging within transfer region104. In some embodiments, in response to this determination, PTU 102 maytransition from the power transfer state to the power save state.

In various embodiments, PRU 212 may be capable of operating in a ChargeComplete Disconnected (CCD) mode. In some embodiments, according to theCCD mode (or “CCCD”), when PTU 102 transitions to the power save state,wireless communication connection 216 may be terminated. In variousembodiments, PRU 212 may be capable of operating in a Charge CompleteConnected (CCC) mode. In some embodiments, while PRU 212 operates in theCCC mode (or “CCCM”), the wireless communication connection 216 betweenPTU 102 and PRU 212 may be maintained. In various embodiments, PRU 212may be configured to use battery power or power from some other sourcein order to engage in wireless communications with PTU 102 via wirelesscommunication connection 216 while operating in the CCC mode. In someembodiments in which PRU 212 is capable of operating in CCC mode, it maynotify PTU 102 of this capability by setting a corresponding bit in aPRU Information bit field of a PRU Static Characteristic. Theembodiments are not limited in this context.

FIG. 3 illustrates an example of an operating environment 300 that maybe representative of various embodiments. In operating environment 300,while operating in the CCC mode, PRU 212 may determine that it onceagain needs to charge the battery of WCD 210. In some embodiments, PRU212 may be able to notify PTU 102 of its need for wireless powertransfer by sending a power transfer request 320 to PTU 102 via wirelesscommunication connection 216. In various embodiments, PRU 212 may beable to send power transfer request 320 by transmitting a PRU DynamicParameter Characteristic or PRU Alert in which it sets a Charge Completebit to a value of 0. The embodiments are not limited in this context.

In some embodiments, PRU 212 may be configured to monitor a rectifiervoltage V_(RECT) while PRU 212 is capable of providing its own power andhas an established wireless communication link—such as wirelesscommunication connection 216—with PTU 102. In various embodiments, PRU212 may be configured to initiate a connection termination procedurewhen V_(RECT) is found to be less than an under-voltage lockout valueV_(RECT_UVLO). In some embodiments, the connection termination proceduremay comprise a Generic Access Profile (GAP) Terminate Connectionprocedure. In various embodiments, PRU 212 may be configured to initiatethe connection termination procedure within a defined amount of timeT_(RECT) following a determination that V_(RECT) has dropped belowV_(RECT_UVLO). In some embodiments, T_(RECT) may be equal to 500 ms. Invarious embodiments, this defined amount of time may be significantlyshorter than the time intervals between long beacons 108. In someembodiments, for example, T_(RECT) may be equal to 500 ms, and longbeacons 108 may be generated at 1000-3000 ms intervals. In various suchembodiments, according to conventional techniques, it may be likely thatthe 500 ms interval elapses and PRU 212 is forced to perform theconnection termination procedure, resulting in undesired termination ofwireless communication connection 216.

Disclosed herein are wireless link management techniques that may beimplemented in some embodiments in order to address this problem.According to various such techniques, a PRU may be configured to observea rectifier voltage while operating in a CCC mode according to which itpossesses a wireless connection with a PTU operating in a power savestate. In some embodiments, the PRU may be configured to observe therectifier voltage in an attempt to detect beacons generated by the PTU.In various embodiments, the PRU may be configured to maintain thewireless connection if it detects beacons, and to terminate the wirelessconnection if it does not detect any beacons. Other embodiments aredescribed and claimed.

FIG. 4 illustrates an example of an operating environment 400 that maybe representative of the implementation of one or more of the disclosedwireless link management techniques according to some embodiments. Inoperating environment 400, while PTU 102 operates in the power savestate and PRU 212 operates in the CCC mode, PRU 212 may monitor V_(RECT)in an attempt to detect short beacons 106 and/or long beacons 108generated by PTU 102. In various embodiments, if PRU 212 detects anyshort beacons 106 and/or long beacons 108, PRU 212 may conclude that itis within transfer region 104 and may maintain wireless communicationconnection 216. In some embodiments, if PRU 212 does not detect anyshort beacon 106 or long beacon 108, it may conclude that it has beenremoved from transfer region 104 and may initiate a connectiontermination procedure, such as a GAP Terminate Connection procedure. Theembodiments are not limited in this context.

In various embodiments, PRU 212 may monitor V_(RECT) in a time intervalwhich is at least x ms long, for example x=1110 ms, or x=3110 ms. Ingeneral, the time interval for monitoring and sampling may be selectedso as to be long enough to result in a reliable detection. In someembodiments, 5 ms sampling and monitoring every 95 ms may be implementedin order to achieve reliable detection of long beacons 108. Theembodiments are not limited to this example.

In various embodiments, following a determination that it needs tocharge the battery of WCD 210, PRU 212 may send a power transfer request420 to PTU 102 and start a timer. In some embodiments, PRU 212 may sendpower transfer request 420 by setting the Charge Complete bit within aPRU Dynamic Parameter Characteristic or PRU Alert to a value of 0. Invarious embodiments, the timer may be used to implement a wait interval.In some embodiments, the wait interval may comprise 0.5 seconds or 1second. The embodiments are not limited to these examples.

In various embodiments, in response to power transfer request 420, PTU102 may determine whether it can provide power to PRU 212. In someembodiments, in response to a determination that it can provide power toPRU 212, PTU 102 may transition to a power transfer state and enable acharge port, and may transmit a power availability notification 422 toPRU 212. In various embodiments, PTU 102 may send power availabilitynotification 422 to PRU 212 by setting PRU Charge Port to a value of 1and setting a Permission field to ‘0000 0000’ in a PRU Control messagethat it transmits to PRU 212. In some embodiments, in response to adetermination that it cannot provide power to PRU 212, PTU 102 may stayin the power save state, and may not enable the charge port. Theembodiments are not limited in this context.

In various embodiments, if PRU 212 receives a power availabilitynotification such as power availability notification 422 prior toexpiration of the wait interval, PRU 212 may maintain wirelesscommunication connection 216 and transition to an on state. In someembodiments, if PRU 212 does not receive a power availabilitynotification prior to expiration of the wait interval, PRU 212 mayinitiate the connection termination procedure. The embodiments are notlimited in this context.

In various embodiments, in order to support the implementation of one ormore of the disclosed techniques, an A4WP base service specification(BSS) may be modified to incorporate a table such as Table 1 below. Theembodiments are not limited in this context.

TABLE 1 Charge start from PTU power save for PRU with CCCM OriginDestination Required Additional required Excep- state state or optionalconditions tions PTU PTU Power Required 0 System errors and Bit NonePower Transfer Field for Permission Save equal to ‘0000 0000’ PRU alertor PRU dynamic parameter characteristic with CC = 0

Operations for the above embodiments may be further described withreference to the following figures and accompanying examples. Some ofthe figures may include a logic flow. Although such figures presentedherein may include a particular logic flow, it can be appreciated thatthe logic flow merely provides an example of how the generalfunctionality as described herein can be implemented. Further, the givenlogic flow does not necessarily have to be executed in the orderpresented unless otherwise indicated. In addition, the given logic flowmay be implemented by a hardware element, a software element executed bya processor, or any combination thereof. The embodiments are not limitedin this context.

FIG. 5 illustrates an example of a logic flow 500 that may berepresentative of the implementation of one or more of the disclosedwireless link management techniques according to some embodiments. Asshown in FIG. 5, logic flow 500 may begin at 502. At 502, a PTU mayoperative in a power save state, a PRU possessing a BLE connection tothe PTU may operate in a boot state, and a Charge Complete bitassociated with the PRU may be set to 1. At 504, a V_(RECT) of the PRUmay be monitored during a monitoring interval. Flow may then proceedfrom 506 depending on whether monitoring of the V_(RECT) resulted in thedetection of a beacon. If a beacon has been detected, flow may pass to508, where the BLE connection may be maintained. If no beacon has beendetected, flow may pass from 506 to 510, where the BLE connection may beterminated. Following either 508 or 510, the logic flow may end.

FIG. 6 illustrates an example of a logic flow 600 that may berepresentative of the implementation of one or more of the disclosedwireless link management techniques according to some embodiments. Asshown in FIG. 6, logic flow 600 may begin at 602. At 602, a PTU mayoperative in a power save state, a PRU possessing a BLE connection tothe PTU may operate in a boot state, and a Charge Complete bitassociated with the PRU may be set to 1. At 604, it may be determinedwhether power is required at the PRU. If it is determined that power isnot required at the PRU, the logic flow may end. If it is determinedthat power is required at the PRU, flow may pass to 606.

At 606, a power transfer request may be sent to the PTU. In someembodiments, the power transfer request may be sent by setting theCharge Complete bit to a value of 0. At 608 a timer may be started inorder to implement a wait interval. Flow may then proceed from 610 basedon whether a power availability notification is received prior toexpiration of the timer. If a power availability notification isreceived prior to expiration of the timer, the BLE connection may bemaintained, and the PRU may transition to an on state. If no poweravailability notification is received prior to expiration of the timer,the BLE connection may be terminated. Following either 612 or 614, thelogic flow may end.

FIG. 7 illustrates an embodiment of a storage medium 700. Storage medium700 may comprise any non-transitory computer-readable storage medium ormachine-readable storage medium, such as an optical, magnetic orsemiconductor storage medium. In various embodiments, storage medium 700may comprise an article of manufacture. In some embodiments, storagemedium 700 may store computer-executable instructions. In variousembodiments, such computer-executable instructions may includecomputer-executable instructions to implement logic flow 500 of FIG. 5and/or logic flow 600 of FIG. 6. In some embodiments, suchcomputer-executable instructions may include computer-executableinstructions to implement a WCD such as WCD 210 and/or to implement aPRU such as PRU 212. Examples of a computer-readable storage medium ormachine-readable storage medium may include any tangible media capableof storing electronic data, including volatile memory or non-volatilememory, removable or non-removable memory, erasable or non-erasablememory, writeable or re-writeable memory, and so forth. Examples ofcomputer-executable instructions may include any suitable type of code,such as source code, compiled code, interpreted code, executable code,static code, dynamic code, object-oriented code, visual code, and thelike. The embodiments are not limited in this context.

FIG. 8 illustrates an embodiment of a communications device 800 that mayimplement one or more of wireless charging station 101, PTU 102, WCD210, PRU 212, logic flow 500, logic flow 600, and storage medium 700. Invarious embodiments, device 800 may comprise a logic circuit 828. Thelogic circuit 828 may include physical circuits to perform operationsdescribed for one or more of wireless charging station 101, PTU 102, WCD210, and PRU 212, for example. As shown in FIG. 8, device 800 mayinclude a radio interface 810, baseband circuitry 820, and computingplatform 830, although the embodiments are not limited to thisconfiguration.

The device 800 may implement some or all of the structure and/oroperations for one or more of wireless charging station 101, PTU 102,WCD 210, PRU 212, logic flow 500, logic flow 600, storage medium 700,and logic circuit 828 in a single computing entity, such as entirelywithin a single device. Alternatively, the device 800 may distributeportions of the structure and/or operations for one or more of wirelesscharging station 101, PTU 102, WCD 210, PRU 212, logic flow 500, logicflow 600, storage medium 700, and logic circuit 828 across multiplecomputing entities using a distributed system architecture, such as aclient-server architecture, a 3-tier architecture, an N-tierarchitecture, a tightly-coupled or clustered architecture, apeer-to-peer architecture, a master-slave architecture, a shareddatabase architecture, and other types of distributed systems. Theembodiments are not limited in this context.

In one embodiment, radio interface 810 may include a component orcombination of components adapted for transmitting and/or receivingsingle-carrier or multi-carrier modulated signals (e.g., includingcomplementary code keying (CCK), orthogonal frequency divisionmultiplexing (OFDM), and/or single-carrier frequency division multipleaccess (SC-FDMA) symbols) although the embodiments are not limited toany specific over-the-air interface or modulation scheme. Radiointerface 810 may include, for example, a receiver 812, a frequencysynthesizer 814, and/or a transmitter 816. Radio interface 810 mayinclude bias controls, a crystal oscillator and/or one or more antennas818-f. In another embodiment, radio interface 810 may use externalvoltage-controlled oscillators (VCOs), surface acoustic wave filters,intermediate frequency (IF) filters and/or RF filters, as desired. Dueto the variety of potential RF interface designs an expansivedescription thereof is omitted.

Baseband circuitry 820 may communicate with radio interface 810 toprocess receive and/or transmit signals and may include, for example, ananalog-to-digital converter 822 for down converting received signals, adigital-to-analog converter 824 for up converting signals fortransmission. Further, baseband circuitry 820 may include a baseband orphysical layer (PHY) processing circuit 826 for PHY link layerprocessing of respective receive/transmit signals. Baseband circuitry820 may include, for example, a medium access control (MAC) processingcircuit 827 for MAC/data link layer processing. Baseband circuitry 820may include a memory controller 832 for communicating with MACprocessing circuit 827 and/or a computing platform 830, for example, viaone or more interfaces 834.

In some embodiments, PHY processing circuit 826 may include a frameconstruction and/or detection module, in combination with additionalcircuitry such as a buffer memory, to construct and/or deconstructcommunication frames. Alternatively or in addition, MAC processingcircuit 827 may share processing for certain of these functions orperform these processes independent of PHY processing circuit 826. Insome embodiments, MAC and PHY processing may be integrated into a singlecircuit.

The computing platform 830 may provide computing functionality for thedevice 800. As shown, the computing platform 830 may include aprocessing component 840. In addition to, or alternatively of, thebaseband circuitry 820, the device 800 may execute processing operationsor logic for one or more of wireless charging station 101, PTU 102, WCD210, PRU 212, logic flow 500, logic flow 600, storage medium 700, andlogic circuit 828 using the processing component 840. The processingcomponent 840 (and/or PHY 826 and/or MAC 827) may comprise varioushardware elements, software elements, or a combination of both. Examplesof hardware elements may include devices, logic devices, components,processors, microprocessors, circuits, processor circuits, circuitelements (e.g., transistors, resistors, capacitors, inductors, and soforth), integrated circuits, application specific integrated circuits(ASIC), programmable logic devices (PLD), digital signal processors(DSP), field programmable gate array (FPGA), memory units, logic gates,registers, semiconductor device, chips, microchips, chip sets, and soforth. Examples of software elements may include software components,programs, applications, computer programs, application programs, systemprograms, software development programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a givenimplementation.

The computing platform 830 may further include other platform components850. Other platform components 850 include common computing elements,such as one or more processors, multi-core processors, co-processors,memory units, chipsets, controllers, peripherals, interfaces,oscillators, timing devices, video cards, audio cards, multimediainput/output (I/O) components (e.g., digital displays), power supplies,and so forth. Examples of memory units may include without limitationvarious types of computer readable and machine readable storage media inthe form of one or more higher speed memory units, such as read-onlymemory (ROM), random-access memory (RAM), dynamic RAM (DRAM),Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM(SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information.

Device 800 may be, for example, an ultra-mobile device, a mobile device,a fixed device, a machine-to-machine (M2M) device, a personal digitalassistant (PDA), a mobile computing device, a smart phone, a telephone,a digital telephone, a cellular telephone, user equipment, eBookreaders, a handset, a one-way pager, a two-way pager, a messagingdevice, a computer, a personal computer (PC), a desktop computer, alaptop computer, a notebook computer, a netbook computer, a handheldcomputer, a tablet computer, a server, a server array or server farm, aweb server, a network server, an Internet server, a work station, amini-computer, a main frame computer, a supercomputer, a networkappliance, a web appliance, a distributed computing system,multiprocessor systems, processor-based systems, consumer electronics,programmable consumer electronics, game devices, display, television,digital television, set top box, wireless access point, base station,node B, subscriber station, mobile subscriber center, radio networkcontroller, router, hub, gateway, bridge, switch, machine, orcombination thereof. Accordingly, functions and/or specificconfigurations of device 800 described herein, may be included oromitted in various embodiments of device 800, as suitably desired.

Embodiments of device 800 may be implemented using single input singleoutput (SISO) architectures. However, certain implementations mayinclude multiple antennas (e.g., antennas 818-f) for transmission and/orreception using adaptive antenna techniques for beamforming or spatialdivision multiple access (SDMA) and/or using MIMO communicationtechniques.

The components and features of device 800 may be implemented using anycombination of discrete circuitry, application specific integratedcircuits (ASICs), logic gates and/or single chip architectures. Further,the features of device 800 may be implemented using microcontrollers,programmable logic arrays and/or microprocessors or any combination ofthe foregoing where suitably appropriate. It is noted that hardware,firmware and/or software elements may be collectively or individuallyreferred to herein as “logic” or “circuit.”

It should be appreciated that the exemplary device 800 shown in theblock diagram of FIG. 8 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would be necessarily bedivided, omitted, or included in embodiments.

FIG. 9 illustrates an embodiment of a wireless network 900. As shown inFIG. 9, wireless network comprises an access point 902 and wirelessstations 904, 906, and 908. In various embodiments, wireless network 900may comprise a wireless local area network (WLAN), such as a WLANimplementing one or more Institute of Electrical and ElectronicsEngineers (IEEE) 802.11 standards (sometimes collectively referred to as“Wi-Fi”). In some other embodiments, wireless network 900 may compriseanother type of wireless network, and/or may implement other wirelesscommunications standards. In various embodiments, for example, wirelessnetwork 900 may comprise a WWAN or WPAN rather than a WLAN. Theembodiments are not limited to this example.

In some embodiments, wireless network 900 may implement one or morebroadband wireless communications standards, such as 3G or 4G standards,including their revisions, progeny, and variants. Examples of 3G or 4Gwireless standards may include without limitation any of the IEEE802.16m and 802.16p standards, 3rd Generation Partnership Project (3GPP)Long Term Evolution (LTE) and LTE-Advanced (LTE-A) standards, andInternational Mobile Telecommunications Advanced (IMT-ADV) standards,including their revisions, progeny and variants. Other suitable examplesmay include, without limitation, Global System for Mobile Communications(GSM)/Enhanced Data Rates for GSM Evolution (EDGE) technologies,Universal Mobile Telecommunications System (UMTS)/High Speed PacketAccess (HSPA) technologies, Worldwide Interoperability for MicrowaveAccess (WiMAX) or the WiMAX II technologies, Code Division MultipleAccess (CDMA) 2000 system technologies (e.g., CDMA2000 1×RTT, CDMA2000EV-DO, CDMA EV-DV, and so forth), High Performance Radio MetropolitanArea Network (HIPERMAN) technologies as defined by the EuropeanTelecommunications Standards Institute (ETSI) Broadband Radio AccessNetworks (BRAN), Wireless Broadband (WiBro) technologies, GSM withGeneral Packet Radio Service (GPRS) system (GSM/GPRS) technologies, HighSpeed Downlink Packet Access (HSDPA) technologies, High Speed OrthogonalFrequency-Division Multiplexing (OFDM) Packet Access (HSOPA)technologies, High-Speed Uplink Packet Access (HSUPA) systemtechnologies, 3GPP Rel. 8-12 of LTE/System Architecture Evolution (SAE),and so forth. The embodiments are not limited in this context.

In various embodiments, wireless stations 904, 906, and 908 maycommunicate with access point 902 in order to obtain connectivity to oneor more external data networks. In some embodiments, for example,wireless stations 904, 906, and 908 may connect to the Internet 912 viaaccess point 902 and access network 910. In various embodiments, accessnetwork 910 may comprise a private network that providessubscription-based Internet-connectivity, such as an Internet ServiceProvider (ISP) network. The embodiments are not limited to this example.

In various embodiments, two or more of wireless stations 904, 906, and908 may communicate with each other directly by exchanging peer-to-peercommunications. For example, in the example of FIG. 9, wireless stations904 and 906 communicate with each other directly by exchangingpeer-to-peer communications 914. In some embodiments, such peer-to-peercommunications may be performed according to one or more Wi-Fi Alliance(WFA) standards. For example, in various embodiments, such peer-to-peercommunications may be performed according to the WFA Wi-Fi Directstandard, 2010 Release. In various embodiments, such peer-to-peercommunications may additionally or alternatively be performed using oneor more interfaces, protocols, and/or standards developed by the WFAWi-Fi Direct Services (WFDS) Task Group. The embodiments are not limitedto these examples.

Various embodiments may be implemented using hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude processors, microprocessors, circuits, circuit elements (e.g.,transistors, resistors, capacitors, inductors, and so forth), integratedcircuits, application specific integrated circuits (ASIC), programmablelogic devices (PLD), digital signal processors (DSP), field programmablegate array (FPGA), logic gates, registers, semiconductor device, chips,microchips, chip sets, and so forth. Examples of software may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor. Some embodiments maybe implemented, for example, using a machine-readable medium or articlewhich may store an instruction or a set of instructions that, ifexecuted by a machine, may cause the machine to perform a method and/oroperations in accordance with the embodiments. Such a machine mayinclude, for example, any suitable processing platform, computingplatform, computing device, processing device, computing system,processing system, computer, processor, or the like, and may beimplemented using any suitable combination of hardware and/or software.The machine-readable medium or article may include, for example, anysuitable type of memory unit, memory device, memory article, memorymedium, storage device, storage article, storage medium and/or storageunit, for example, memory, removable or non-removable media, erasable ornon-erasable media, writeable or re-writeable media, digital or analogmedia, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM),Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW),optical disk, magnetic media, magneto-optical media, removable memorycards or disks, various types of Digital Versatile Disk (DVD), a tape, acassette, or the like. The instructions may include any suitable type ofcode, such as source code, compiled code, interpreted code, executablecode, static code, dynamic code, encrypted code, and the like,implemented using any suitable high-level, low-level, object-oriented,visual, compiled and/or interpreted programming language.

The following examples pertain to further embodiments:

Example 1 is an apparatus, comprising a memory, and logic for a powerreceiving unit (PRU), at least a portion of the logic implemented incircuitry coupled to the memory, the logic to initiate an operating modetransition to cause the PRU to operate in a charge complete connected(CCC) mode, monitor a rectifier voltage of the PRU to check for powerbeacons of a power transmitting unit (PTU) during a monitoring interval,and in response to a detection of at least one power beacon during themonitoring interval, determine to maintain a wireless connection withthe PTU.

Example 2 is the apparatus of Example 1, the logic to initiate aconnection termination procedure to terminate the wireless connectionwhen no power beacon is detected during the monitoring interval.

Example 3 is the apparatus of Example 2, the connection terminationprocedure to comprise a Generic Access Profile (GAP) TerminateConnection procedure.

Example 4 is the apparatus of any of Examples 1 to 3, the wirelessconnection to comprise a Bluetooth Low Energy (BLE) connection.

Example 5 is the apparatus of any of Examples 1 to 4, the logic to set abit of a PRU Static Characteristic associated with the PRU to a valueindicating that the PRU is capable of operating in the CCC mode.

Example 6 is the apparatus of Example 5, the bit to be comprised in aPRU Information bit field of the PRU Static Characteristic.

Example 7 is the apparatus of any of Examples 1 to 6, a duration of themonitoring interval to exceed a duration of a time interval between longbeacons of the PTU.

Example 8 is the apparatus of Example 7, the time interval between longbeacons of the PTU to comprise a duration within a range of 1000-3000ms, inclusive.

Example 9 is the apparatus of any of Examples 1 to 8, the logic todetermine, during operation of the PRU in the CCC mode, whether power isrequired at the PRU, and in response to a determination that power isrequired at the PRU, generate a power transfer request for transmissionto the PTU.

Example 10 is the apparatus of Example 9, the generation of the powertransfer request to include setting a Charge Complete bit to a value of0.

Example 11 is the apparatus of Example 10, the Charge Complete bit to becomprised in a PRU Dynamic Parameter Characteristic associated with thePRU.

Example 12 is the apparatus of Example 10, the Charge Complete bit to becomprised in a PRU Alert.

Example 13 is the apparatus of any of Examples 9 to 12, the logic toinitiate a connection termination procedure to terminate the wirelessconnection in response to a determination, upon an expiration of a waitinterval following a transmission of the power transfer request, that nopower availability notification has been received from the PTU.

Example 14 is the apparatus of Example 13, the connection terminationprocedure to comprise a Generic Access Profile (GAP) TerminateConnection procedure.

Example 15 is the apparatus of any of Examples 9 to 12, the logic todetermine to maintain the wireless connection based on receipt of apower availability notification from the PTU during a wait intervalfollowing a transmission of the power transfer request.

Example 16 is the apparatus of Example 15, the wait interval to comprisea duration of 0.5 seconds.

Example 17 is the apparatus of Example 15, the wait interval to comprisea duration of 1.0 seconds.

Example 18 is the apparatus of any of Examples 15 to 17, the logic totransition the PRU to an on state in response to receipt of the poweravailability notification.

Example 19 is the apparatus of Example 18, the logic to transition thePRU from a boot state to the on state.

Example 20 is the apparatus of any of Examples 15 to 19, the poweravailability notification to comprise a PRU Control message.

Example 21 is the apparatus of Example 20, the PRU Control message toinclude a PRU Charge Port field comprising a value of 1.

Example 22 is the apparatus of any of Examples 20 to 21, the PRU Controlmessage to include a Permission field comprising a value of ‘0000 0000’.

Example 23 is a system, comprising an apparatus according to any ofExamples 1 to 22, and at least one radio frequency (RF) transceiver.

Example 24 is the system of Example 23, comprising at least one RFantenna.

Example 25 is the system of any of Examples 23 to 24, comprising atleast one processor.

Example 26 is an apparatus, comprising a memory, and logic for a powertransmitting unit (PTU), at least a portion of the logic implemented incircuitry coupled to the memory, the logic to detect, during operationof the PTU in a power save state, a power transfer request of a chargecomplete connected mode (CCC-mode) power receiving unit (PRU), determinewhether the PTU can provide power to the CCC-mode PRU, and in responseto a determination that the PTU can provide power to the CCC-mode PRU,transition the PTU to a power transfer state and generate a poweravailability notification for transmission to the CCC-mode PRU.

Example 27 is the apparatus of Example 26, the logic to determine tomaintain the power save state in response to a determination that thePTU cannot provide power to the CCC-mode PRU.

Example 28 is the apparatus of any of Examples 26 to 27, the poweravailability notification to comprise a PRU Control message.

Example 29 is the apparatus of any of Examples 26 to 28, the logic toenable a charge port in response to the determination that the PTU canprovide power to the CCC-mode PRU.

Example 30 is the apparatus of Example 29, the power availabilitynotification to indicate the enablement of the charge port.

Example 31 is the apparatus of Example 30, the power availabilitynotification to include a PRU Charge Port field comprising a valueindicating the enablement of the charge port.

Example 32 is the apparatus of any of Examples 26 to 31, the poweravailability notification to include a Permission field comprising avalue of ‘0000 0000’.

Example 33 is the apparatus of any of Examples 26 to 32, the logic todetermine that the CCC-mode PRU is capable of operating according to thecharge complete connected mode based on a value of a bit of a PRU StaticCharacteristic associated with the CCC-mode PRU.

Example 34 is the apparatus of Example 33, the bit to be comprised in aPRU Information bit field of the PRU Static Characteristic.

Example 35 is the apparatus of any of Examples 26 to 34, the powertransfer request to contain a Charge Complete bit comprising a value of0.

Example 36 is the apparatus of any of Examples 26 to 35, the powertransfer request to comprise a PRU Dynamic Parameter Characteristicassociated with the CCC-mode PRU.

Example 37 is the apparatus of any of Examples 26 to 35, the powertransfer request to comprise a PRU Alert.

Example 38 is the apparatus of any of Examples 26 to 37, the logic toinitiate the operation in the power save state based on receipt of acharge completion notification from the CCC-mode PRU.

Example 39 is the apparatus of Example 38, the charge completionnotification to comprise a Charge Complete bit comprising a value of 1.

Example 40 is the apparatus of any of Examples 38 to 39, the chargecompletion notification to comprise a PRU Dynamic ParameterCharacteristic associated with the CCC-mode PRU.

Example 41 is the apparatus of any of Examples 38 to 39, the chargecompletion notification to comprise a PRU Alert.

Example 42 is the apparatus of any of Examples 26 to 41, the powertransfer request to be received via a Bluetooth Low Energy (BLE)connection with the CCC-mode PRU.

Example 43 is a system, comprising an apparatus according to any ofExamples 26 to 42, and at least one radio frequency (RF) transceiver.

Example 44 is the system of Example 43, comprising at least one RFantenna.

Example 45 is the system of any of Examples 43 to 44, comprising atleast one processor.

Example 46 is at least one non-transitory computer-readable storagemedium comprising a set of instructions that, in response to beingexecuted at a power receiving unit (PRU), cause the PRU to initiate anoperating mode transition to transition to a charge complete connected(CCC) mode, monitor a rectifier voltage of the PRU to check for powerbeacons of a power transmitting unit (PTU) during a monitoring interval,and in response to a detection of at least one power beacon during themonitoring interval, determine to maintain a wireless connection withthe PTU.

Example 47 is the at least one non-transitory computer-readable storagemedium of Example 46, comprising instructions that, in response to beingexecuted at the PRU, cause the PRU to initiate a connection terminationprocedure to terminate the wireless connection when no power beacon isdetected during the monitoring interval.

Example 48 is the at least one non-transitory computer-readable storagemedium of Example 47, the connection termination procedure to comprise aGeneric Access Profile (GAP) Terminate Connection procedure.

Example 49 is the at least one non-transitory computer-readable storagemedium of any of Examples 46 to 48, the wireless connection to comprisea Bluetooth Low Energy (BLE) connection.

Example 50 is the at least one non-transitory computer-readable storagemedium of any of Examples 46 to 49, comprising instructions that, inresponse to being executed at the PRU, cause the PRU to set a bit of aPRU Static Characteristic associated with the PRU to a value indicatingthat the PRU is capable of operating in the CCC mode.

Example 51 is the at least one non-transitory computer-readable storagemedium of Example 50, the bit to be comprised in a PRU Information bitfield of the PRU Static Characteristic.

Example 52 is the at least one non-transitory computer-readable storagemedium of any of Examples 46 to 51, a duration of the monitoringinterval to exceed a duration of a time interval between long beacons ofthe PTU.

Example 53 is the at least one non-transitory computer-readable storagemedium of Example 52, the time interval between long beacons of the PTUto comprise a duration within a range of 1000-3000 ms, inclusive.

Example 54 is the at least one non-transitory computer-readable storagemedium of any of Examples 46 to 53, comprising instructions that, inresponse to being executed at the PRU, cause the PRU to determine,during operation in the CCC mode, whether power is required at the PRU,and in response to a determination that power is required at the PRU,generate a power transfer request for transmission to the PTU.

Example 55 is the at least one non-transitory computer-readable storagemedium of Example 54, the generation of the power transfer request toinclude setting a Charge Complete bit to a value of 0.

Example 56 is the at least one non-transitory computer-readable storagemedium of Example 55, the Charge Complete bit to be comprised in a PRUDynamic Parameter Characteristic associated with the PRU.

Example 57 is the at least one non-transitory computer-readable storagemedium of Example 55, the Charge Complete bit to be comprised in a PRUAlert.

Example 58 is the at least one non-transitory computer-readable storagemedium of any of Examples 54 to 57, comprising instructions that, inresponse to being executed at the PRU, cause the PRU to initiate aconnection termination procedure to terminate the wireless connection inresponse to a determination, upon an expiration of a wait intervalfollowing a transmission of the power transfer request, that no poweravailability notification has been received from the PTU.

Example 59 is the at least one non-transitory computer-readable storagemedium of Example 58, the connection termination procedure to comprise aGeneric Access Profile (GAP) Terminate Connection procedure.

Example 60 is the at least one non-transitory computer-readable storagemedium of any of Examples 54 to 57, comprising instructions that, inresponse to being executed at the PRU, cause the PRU to determine tomaintain the wireless connection based on receipt of a poweravailability notification from the PTU during a wait interval followinga transmission of the power transfer request.

Example 61 is the at least one non-transitory computer-readable storagemedium of Example 60, the wait interval to comprise a duration of 0.5seconds.

Example 62 is the at least one non-transitory computer-readable storagemedium of Example 60, the wait interval to comprise a duration of 1.0seconds.

Example 63 is the at least one non-transitory computer-readable storagemedium of any of Examples 60 to 62, comprising instructions that, inresponse to being executed at the PRU, cause the PRU to transition to anon state in response to receipt of the power availability notification.

Example 64 is the at least one non-transitory computer-readable storagemedium of Example 63, comprising instructions that, in response to beingexecuted at the PRU, cause the PRU to transition from a boot state tothe on state.

Example 65 is the at least one non-transitory computer-readable storagemedium of any of Examples 60 to 64, the power availability notificationto comprise a PRU Control message.

Example 66 is the at least one non-transitory computer-readable storagemedium of Example 65, the PRU Control message to include a PRU ChargePort field comprising a value of 1.

Example 67 is the at least one non-transitory computer-readable storagemedium of any of Examples 65 to 66, the PRU Control message to include aPermission field comprising a value of ‘0000 0000’.

Example 68 is at least one non-transitory computer-readable storagemedium comprising a set of instructions that, in response to beingexecuted at a power transmitting unit (PTU), cause the PTU to detect,during operation in a power save state, a power transfer request of acharge complete connected mode (CCC-mode) power receiving unit (PRU),determine whether the PTU can provide power to the CCC-mode PRU, and inresponse to a determination that the PTU can provide power to theCCC-mode PRU, transition to a power transfer state and generate a poweravailability notification for transmission to the CCC-mode PRU.

Example 69 is the at least one non-transitory computer-readable storagemedium of Example 68, comprising instructions that, in response to beingexecuted at the PTU, cause the PTU to determine to maintain the powersave state in response to a determination that the PTU cannot providepower to the CCC-mode PRU.

Example 70 is the at least one non-transitory computer-readable storagemedium of any of Examples 68 to 69, the power availability notificationto comprise a PRU Control message.

Example 71 is the at least one non-transitory computer-readable storagemedium of any of Examples 68 to 70, comprising instructions that, inresponse to being executed at the PTU, cause the PTU to enable a chargeport in response to the determination that the PTU can provide power tothe CCC-mode PRU.

Example 72 is the at least one non-transitory computer-readable storagemedium of Example 71, the power availability notification to indicatethe enablement of the charge port.

Example 73 is the at least one non-transitory computer-readable storagemedium of Example 72, the power availability notification to include aPRU Charge Port field comprising a value indicating the enablement ofthe charge port.

Example 74 is the at least one non-transitory computer-readable storagemedium of any of Examples 68 to 73, the power availability notificationto include a Permission field comprising a value of ‘0000 0000’.

Example 75 is the at least one non-transitory computer-readable storagemedium of any of Examples 68 to 74, comprising instructions that, inresponse to being executed at the PTU, cause the PTU to determine thatthe CCC-mode PRU is capable of operating according to the chargecomplete connected mode based on a value of a bit of a PRU StaticCharacteristic associated with the CCC-mode PRU.

Example 76 is the at least one non-transitory computer-readable storagemedium of Example 75, the bit to be comprised in a PRU Information bitfield of the PRU Static Characteristic.

Example 77 is the at least one non-transitory computer-readable storagemedium of any of Examples 68 to 76, the power transfer request tocontain a Charge Complete bit comprising a value of 0.

Example 78 is the at least one non-transitory computer-readable storagemedium of any of Examples 68 to 77, the power transfer request tocomprise a PRU Dynamic Parameter Characteristic associated with theCCC-mode PRU.

Example 79 is the at least one non-transitory computer-readable storagemedium of any of Examples 68 to 77, the power transfer request tocomprise a PRU Alert.

Example 80 is the at least one non-transitory computer-readable storagemedium of any of Examples 68 to 79, comprising instructions that, inresponse to being executed at the PTU, cause the PTU to initiate theoperation in the power save state based on receipt of a chargecompletion notification from the CCC-mode PRU.

Example 81 is the at least one non-transitory computer-readable storagemedium of Example 80, the charge completion notification to comprise aCharge Complete bit comprising a value of 1.

Example 82 is the at least one non-transitory computer-readable storagemedium of any of Examples 80 to 81, the charge completion notificationto comprise a PRU Dynamic Parameter Characteristic associated with theCCC-mode PRU.

Example 83 is the at least one non-transitory computer-readable storagemedium of any of Examples 80 to 81, the charge completion notificationto comprise a PRU Alert.

Example 84 is the at least one non-transitory computer-readable storagemedium of any of Examples 68 to 83, the power transfer request to bereceived via a Bluetooth Low Energy (BLE) connection with the CCC-modePRU.

Example 85 is a method, comprising initiating an operating modetransition to cause a power receiving unit (PRU) to operate in a chargecomplete connected (CCC) mode, monitoring a rectifier voltage of the PRUto check for power beacons of a power transmitting unit (PTU) during amonitoring interval, and in response to a detection of at least onepower beacon during the monitoring interval, determining to maintain awireless connection with the PTU.

Example 86 is the method of Example 85, comprising initiating aconnection termination procedure to terminate the wireless connectionwhen no power beacon is detected during the monitoring interval.

Example 87 is the method of Example 86, the connection terminationprocedure to comprise a Generic Access Profile (GAP) TerminateConnection procedure.

Example 88 is the method of any of Examples 85 to 87, the wirelessconnection to comprise a Bluetooth Low Energy (BLE) connection.

Example 89 is the method of any of Examples 85 to 88, comprising settinga bit of a PRU Static Characteristic associated with the PRU to a valueindicating that the PRU is capable of operating in the CCC mode.

Example 90 is the method of Example 89, the bit to be comprised in a PRUInformation bit field of the PRU Static Characteristic.

Example 91 is the method of any of Examples 85 to 90, a duration of themonitoring interval to exceed a duration of a time interval between longbeacons of the PTU.

Example 92 is the method of Example 91, the time interval between longbeacons of the PTU to comprise a duration within a range of 1000-3000ms, inclusive.

Example 93 is the method of any of Examples 85 to 92, comprisingdetermining, during operation of the PRU in the CCC mode, whether poweris required at the PRU, and in response to a determination that power isrequired at the PRU, generating a power transfer request fortransmission to the PTU.

Example 94 is the method of Example 93, the generation of the powertransfer request to include setting a Charge Complete bit to a value of0.

Example 95 is the method of Example 94, the Charge Complete bit to becomprised in a PRU Dynamic Parameter Characteristic associated with thePRU.

Example 96 is the method of Example 94, the Charge Complete bit to becomprised in a PRU Alert.

Example 97 is the method of any of Examples 93 to 96, comprisinginitiating a connection termination procedure to terminate the wirelessconnection in response to a determination, upon an expiration of a waitinterval following a transmission of the power transfer request, that nopower availability notification has been received from the PTU.

Example 98 is the method of Example 97, the connection terminationprocedure to comprise a Generic Access Profile (GAP) TerminateConnection procedure.

Example 99 is the method of any of Examples 93 to 96, comprisingdetermining to maintain the wireless connection based on receipt of apower availability notification from the PTU during a wait intervalfollowing a transmission of the power transfer request.

Example 100 is the method of Example 99, the wait interval to comprise aduration of 0.5 seconds.

Example 101 is the method of Example 99, the wait interval to comprise aduration of 1.0 seconds.

Example 102 is the method of any of Examples 99 to 101, comprisingtransitioning the PRU to an on state in response to receipt of the poweravailability notification.

Example 103 is the method of Example 102, comprising transitioning thePRU from a boot state to the on state.

Example 104 is the method of any of Examples 99 to 103, the poweravailability notification to comprise a PRU Control message.

Example 105 is the method of Example 104, the PRU Control message toinclude a PRU Charge Port field comprising a value of 1.

Example 106 is the method of any of Examples 104 to 105, the PRU Controlmessage to include a Permission field comprising a value of ‘0000 0000’.

Example 107 is at least one non-transitory computer-readable storagemedium comprising a set of instructions that, in response to beingexecuted on a computing device, cause the computing device to perform amethod according to any of Examples 85 to 106.

Example 108 is an apparatus, comprising means for performing a methodaccording to any of Examples 85 to 106.

Example 109 is a system, comprising the apparatus of Example 108, and atleast one radio frequency (RF) transceiver.

Example 110 is the system of Example 109, comprising at least one RFantenna.

Example 111 is the system of any of Examples 109 to 110, comprising atleast one processor.

Example 112 is a method, comprising detecting, during operation of apower transmitting unit (PTU) in a power save state, a power transferrequest of a charge complete connected mode (CCC-mode) power receivingunit (PRU), determining whether the PTU can provide power to theCCC-mode PRU, and in response to a determination that the PTU canprovide power to the CCC-mode PRU, transitioning the PTU to a powertransfer state and generating a power availability notification fortransmission to the CCC-mode PRU.

Example 113 is the method of Example 112, comprising determining tomaintain the power save state in response to a determination that thePTU cannot provide power to the CCC-mode PRU.

Example 114 is the method of any of Examples 112 to 113, the poweravailability notification to comprise a PRU Control message.

Example 115 is the method of any of Examples 112 to 114, comprisingenabling a charge port in response to the determination that the PTU canprovide power to the CCC-mode PRU.

Example 116 is the method of Example 115, the power availabilitynotification to indicate the enablement of the charge port.

Example 117 is the method of Example 116, the power availabilitynotification to include a PRU Charge Port field comprising a valueindicating the enablement of the charge port.

Example 118 is the method of any of Examples 112 to 117, the poweravailability notification to include a Permission field comprising avalue of ‘0000 0000’.

Example 119 is the method of any of Examples 112 to 118, comprisingdetermining that the CCC-mode PRU is capable of operating according tothe charge complete connected mode based on a value of a bit of a PRUStatic Characteristic associated with the CCC-mode PRU.

Example 120 is the method of Example 119, the bit to be comprised in aPRU Information bit field of the PRU Static Characteristic.

Example 121 is the method of any of Examples 112 to 120, the powertransfer request to contain a Charge Complete bit comprising a value of0.

Example 122 is the method of any of Examples 112 to 121, the powertransfer request to comprise a PRU Dynamic Parameter Characteristicassociated with the CCC-mode PRU.

Example 123 is the method of any of Examples 112 to 121, the powertransfer request to comprise a PRU Alert.

Example 124 is the method of any of Examples 112 to 123, comprisinginitiating the operation in the power save state based on receipt of acharge completion notification from the CCC-mode PRU.

Example 125 is the method of Example 124, the charge completionnotification to comprise a Charge Complete bit comprising a value of 1.

Example 126 is the method of any of Examples 124 to 125, the chargecompletion notification to comprise a PRU Dynamic ParameterCharacteristic associated with the CCC-mode PRU.

Example 127 is the method of any of Examples 124 to 125, the chargecompletion notification to comprise a PRU Alert.

Example 128 is the method of any of Examples 112 to 127, the powertransfer request to be received via a Bluetooth Low Energy (BLE)connection with the CCC-mode PRU.

Example 129 is at least one non-transitory computer-readable storagemedium comprising a set of instructions that, in response to beingexecuted on a computing device, cause the computing device to perform amethod according to any of Examples 112 to 128.

Example 130 is an apparatus, comprising means for performing a methodaccording to any of Examples 112 to 128.

Example 131 is a system, comprising the apparatus of Example 130, and atleast one radio frequency (RF) transceiver.

Example 132 is the system of Example 131, comprising at least one RFantenna.

Example 133 is the system of any of Examples 131 to 132, comprising atleast one processor.

Example 134 is an apparatus, comprising means for initiating anoperating mode transition to cause a power receiving unit (PRU) tooperate in a charge complete connected (CCC) mode, means for monitoringa rectifier voltage of the PRU to check for power beacons of a powertransmitting unit (PTU) during a monitoring interval, and means fordetermining to maintain a wireless connection with the PTU in responseto a detection of at least one power beacon during the monitoringinterval.

Example 135 is the apparatus of Example 134, comprising means forinitiating a connection termination procedure to terminate the wirelessconnection when no power beacon is detected during the monitoringinterval.

Example 136 is the apparatus of Example 135, the connection terminationprocedure to comprise a Generic Access Profile (GAP) TerminateConnection procedure.

Example 137 is the apparatus of any of Examples 134 to 136, the wirelessconnection to comprise a Bluetooth Low Energy (BLE) connection.

Example 138 is the apparatus of any of Examples 134 to 137, comprisingmeans for setting a bit of a PRU Static Characteristic associated withthe PRU to a value indicating that the PRU is capable of operating inthe CCC mode.

Example 139 is the apparatus of Example 138, the bit to be comprised ina PRU Information bit field of the PRU Static Characteristic.

Example 140 is the apparatus of any of Examples 134 to 139, a durationof the monitoring interval to exceed a duration of a time intervalbetween long beacons of the PTU.

Example 141 is the apparatus of Example 140, the time interval betweenlong beacons of the PTU to comprise a duration within a range of1000-3000 ms, inclusive.

Example 142 is the apparatus of any of Examples 134 to 141, comprisingmeans for determining, during operation of the PRU in the CCC mode,whether power is required at the PRU, and means for generating a powertransfer request for transmission to the PTU in response to adetermination that power is required at the PRU.

Example 143 is the apparatus of Example 142, the generation of the powertransfer request to include setting a Charge Complete bit to a value of0.

Example 144 is the apparatus of Example 143, the Charge Complete bit tobe comprised in a PRU Dynamic Parameter Characteristic associated withthe PRU.

Example 145 is the apparatus of Example 143, the Charge Complete bit tobe comprised in a PRU Alert.

Example 146 is the apparatus of any of Examples 142 to 145, comprisingmeans for initiating a connection termination procedure to terminate thewireless connection in response to a determination, upon an expirationof a wait interval following a transmission of the power transferrequest, that no power availability notification has been received fromthe PTU.

Example 147 is the apparatus of Example 146, the connection terminationprocedure to comprise a Generic Access Profile (GAP) TerminateConnection procedure.

Example 148 is the apparatus of any of Examples 142 to 145, comprisingmeans for determining to maintain the wireless connection based onreceipt of a power availability notification from the PTU during a waitinterval following a transmission of the power transfer request.

Example 149 is the apparatus of Example 148, the wait interval tocomprise a duration of 0.5 seconds.

Example 150 is the apparatus of Example 148, the wait interval tocomprise a duration of 1.0 seconds.

Example 151 is the apparatus of any of Examples 148 to 150, comprisingmeans for transitioning the PRU to an on state in response to receipt ofthe power availability notification.

Example 152 is the apparatus of Example 151, comprising means fortransitioning the PRU from a boot state to the on state.

Example 153 is the apparatus of any of Examples 148 to 152, the poweravailability notification to comprise a PRU Control message.

Example 154 is the apparatus of Example 153, the PRU Control message toinclude a PRU Charge Port field comprising a value of 1.

Example 155 is the apparatus of any of Examples 153 to 154, the PRUControl message to include a Permission field comprising a value of‘0000 0000’.

Example 156 is a system, comprising an apparatus according to any ofExamples 134 to 155, and at least one radio frequency (RF) transceiver.

Example 157 is the system of Example 156, comprising at least one RFantenna.

Example 158 is the system of any of Examples 156 to 157, comprising atleast one processor.

Example 159 is an apparatus, comprising means for detecting, duringoperation of a power transmitting unit (PTU) in a power save state, apower transfer request of a charge complete connected mode (CCC-mode)power receiving unit (PRU), means for determining whether the PTU canprovide power to the CCC-mode PRU, and means for transitioning the PTUto a power transfer state and generating a power availabilitynotification for transmission to the CCC-mode PRU in response to adetermination that the PTU can provide power to the CCC-mode PRU.

Example 160 is the apparatus of Example 159, comprising means fordetermining to maintain the power save state in response to adetermination that the PTU cannot provide power to the CCC-mode PRU.

Example 161 is the apparatus of any of Examples 159 to 160, the poweravailability notification to comprise a PRU Control message.

Example 162 is the apparatus of any of Examples 159 to 161, comprisingmeans for enabling a charge port in response to the determination thatthe PTU can provide power to the CCC-mode PRU.

Example 163 is the apparatus of Example 162, the power availabilitynotification to indicate the enablement of the charge port.

Example 164 is the apparatus of Example 163, the power availabilitynotification to include a PRU Charge Port field comprising a valueindicating the enablement of the charge port.

Example 165 is the apparatus of any of Examples 159 to 164, the poweravailability notification to include a Permission field comprising avalue of ‘0000 0000’.

Example 166 is the apparatus of any of Examples 159 to 165, comprisingmeans for determining that the CCC-mode PRU is capable of operatingaccording to the charge complete connected mode based on a value of abit of a PRU Static Characteristic associated with the CCC-mode PRU.

Example 167 is the apparatus of Example 166, the bit to be comprised ina PRU Information bit field of the PRU Static Characteristic.

Example 168 is the apparatus of any of Examples 159 to 167, the powertransfer request to contain a Charge Complete bit comprising a value of0.

Example 169 is the apparatus of any of Examples 159 to 168, the powertransfer request to comprise a PRU Dynamic Parameter Characteristicassociated with the CCC-mode PRU.

Example 170 is the apparatus of any of Examples 159 to 168, the powertransfer request to comprise a PRU Alert.

Example 171 is the apparatus of any of Examples 159 to 170, comprisingmeans for initiating the operation in the power save state based onreceipt of a charge completion notification from the CCC-mode PRU.

Example 172 is the apparatus of Example 171, the charge completionnotification to comprise a Charge Complete bit comprising a value of 1.

Example 173 is the apparatus of any of Examples 171 to 172, the chargecompletion notification to comprise a PRU Dynamic ParameterCharacteristic associated with the CCC-mode PRU.

Example 174 is the apparatus of any of Examples 171 to 172, the chargecompletion notification to comprise a PRU Alert.

Example 175 is the apparatus of any of Examples 159 to 174, the powertransfer request to be received via a Bluetooth Low Energy (BLE)connection with the CCC-mode PRU.

Example 176 is a system, comprising an apparatus according to any ofExamples 159 to 175, and at least one radio frequency (RF) transceiver.

Example 177 is the system of Example 176, comprising at least one RFantenna.

Example 178 is the system of any of Examples 176 to 177, comprising atleast one processor.

Numerous specific details have been set forth herein to provide athorough understanding of the embodiments. It will be understood bythose skilled in the art, however, that the embodiments may be practicedwithout these specific details. In other instances, well-knownoperations, components, and circuits have not been described in detailso as not to obscure the embodiments. It can be appreciated that thespecific structural and functional details disclosed herein may berepresentative and do not necessarily limit the scope of theembodiments.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. These terms are not intendedas synonyms for each other. For example, some embodiments may bedescribed using the terms “connected” and/or “coupled” to indicate thattwo or more elements are in direct physical or electrical contact witheach other. The term “coupled,” however, may also mean that two or moreelements are not in direct contact with each other, but yet stillco-operate or interact with each other.

Unless specifically stated otherwise, it may be appreciated that termssuch as “processing,” “computing,” “calculating,” “determining,” or thelike, refer to the action and/or processes of a computer or computingsystem, or similar electronic computing device, that manipulates and/ortransforms data represented as physical quantities (e.g., electronic)within the computing system's registers and/or memories into other datasimilarly represented as physical quantities within the computingsystem's memories, registers or other such information storage,transmission or display devices. The embodiments are not limited in thiscontext.

It should be noted that the methods described herein do not have to beexecuted in the order described, or in any particular order. Moreover,various activities described with respect to the methods identifiedherein can be executed in serial or parallel fashion.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific embodimentsshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments. It is to be understood that the abovedescription has been made in an illustrative fashion, and not arestrictive one. Combinations of the above embodiments, and otherembodiments not specifically described herein will be apparent to thoseof skill in the art upon reviewing the above description. Thus, thescope of various embodiments includes any other applications in whichthe above compositions, structures, and methods are used.

It is emphasized that the Abstract of the Disclosure is provided tocomply with 37 C.F.R. § 1.72(b), requiring an abstract that will allowthe reader to quickly ascertain the nature of the technical disclosure.It is submitted with the understanding that it will not be used tointerpret or limit the scope or meaning of the claims. In addition, inthe foregoing Detailed Description, it can be seen that various featuresare grouped together in a single embodiment for the purpose ofstreamlining the disclosure. This method of disclosure is not to beinterpreted as reflecting an intention that the claimed embodimentsrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject matter lies in lessthan all features of a single disclosed embodiment. Thus the followingclaims are hereby incorporated into the Detailed Description, with eachclaim standing on its own as a separate preferred embodiment. In theappended claims, the terms “including” and “in which” are used as theplain-English equivalents of the respective terms “comprising” and“wherein,” respectively. Moreover, the terms “first,” “second,” and“third,” etc. are used merely as labels, and are not intended to imposenumerical requirements on their objects.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. An apparatus, comprising: a memory; and logic fora power receiving unit (PRU), at least a portion of the logicimplemented in circuitry coupled to the memory, the logic to: set chargecomplete equal to zero in a PRU Dynamic Parameter Characteristic or PRUAlert, during operation of the PRU in charge complete connected mode(CCCM), while power transfer unit (PTU) is in a power save state fortransmission to the PTU to indicate a charge is required, and enable acharge port to enable power transfer from the PTU in response topermission by the PTU to enable the charge port.
 2. The apparatus ofclaim 1, the logic to indicate capability of CCCM in a PRU StaticCharacteristic.
 3. The apparatus of claim 1, the logic to be capable ofa charge complete disconnected mode (CCDM).
 4. The apparatus of claim 1,the logic to indicate charge complete equals one if charging is notrequired.
 5. The apparatus of claim 1, the logic to maintain a Bluetoothlow energy (BLE) connection with the PTU while in the CCCM.
 6. Theapparatus of claim 1, the logic to transition to a PRU boot state afterindicating charge complete equals one.
 7. The apparatus of claim 1, thelogic to: monitor a rectifier voltage of the PRU to check for powerbeacons from power transmitting unit (PTU) during a monitoring interval;and in response to a detection of at least one power beacon during themonitoring interval, determine to maintain a wireless connection withthe PTU.
 8. The apparatus of claim 7, the logic to initiate a connectiontermination procedure to terminate the wireless connection when no powerbeacon is detected during the monitoring interval.
 9. The apparatus ofclaim 7, a duration of the monitoring interval to exceed a duration of atime interval between long beacons of the PTU.
 10. A system, comprising:the apparatus of claim 1; at least one radio frequency (RF) transceiver;and at least one RF antenna.
 11. At least one non-transitorycomputer-readable storage medium comprising a set of instructions that,in response to being executed at a power receiving unit (PRU), cause thePRU to: set charge complete equal to zero in a PRU Dynamic ParameterCharacteristic or PRU Alert, during operation of the PRU in chargecomplete connected mode (CCCM), while power transfer unit (PTU) is in apower save state for transmission to the PTU to indicate a charge isrequired, and enable a charge port to enable power transfer from the PTUin response to permission by the PTU to enable the charge port.
 12. Theat least one non-transitory computer-readable storage medium of claim11, the PRU to indicate capability of CCCM in a PRU StaticCharacteristic.
 13. The at least one non-transitory computer-readablestorage medium of claim 11, the PRU to be capable of a charge completedisconnected mode (CCDM).
 14. The at least one non-transitorycomputer-readable storage medium of claim 11, the PRU to indicate chargecomplete equals one if charging is not required.
 15. The at least onenon-transitory computer-readable storage medium of claim 11, the PRU tomaintain a Bluetooth low energy (BLE) connection with the PTU while inthe CCCM.
 16. The at least one non-transitory computer-readable storagemedium of claim 11, the PRU to transition to a PRU boot state afterindicating charge complete equals one.
 17. The at least onenon-transitory computer-readable storage medium of claim 11, the PRU to:monitor a rectifier voltage of the PRU to check for power beacons frompower transmitting unit (PTU) during a monitoring interval; and inresponse to a detection of at least one power beacon during themonitoring interval, determine to maintain a wireless connection withthe PTU.
 18. The at least one non-transitory computer-readable storagemedium of claim 17, the PRU to initiate a connection terminationprocedure to terminate the wireless connection when no power beacon isdetected during the monitoring interval.
 19. The at least onenon-transitory computer-readable storage medium of claim 17, a durationof the monitoring interval to exceed a duration of a time intervalbetween long beacons of the PTU.